Remote decoupled application persistent state apparatuses, methods and systems

ABSTRACT

The REMOTE DECOUPLED APPLICATION PERSISTENT STATE APPARATUSES, METHODS AND SYSTEMS (“P-STATE”) transforms purchase action input, cookie states search criteria input, and cookie states selection input via P-STATE components such as cookie/states storage (“CSS”) component; cookie states search presentation (“CSSP”) component; and cookie/states reload/recreate (“CSRR”) component, into cookie state presentation outputs.

PRIORITY CLAIM

This application claims priority to U.S. Patent Application Ser. No.61/798,483, filed Mar. 15, 2013 and entitled “Remote DecoupledApplication Persistent State Apparatuses, Methods and Systems”. Thisapplication also claims priority to U.S. patent application Ser. No.13/624,779, filed Sep. 21, 2012 and entitled “Wallet Service EnrollmentPlatform Apparatuses, Methods and Systems,” which is acontinuation-in-part and claims priority to U.S. patent application Ser.No. 13/589,053, filed Aug. 17, 2012 and entitled “WALLET SERVICEENROLLMENT PLATFORM APPARATUSES, METHODS AND SYSTEMS,” which in turnclaims priority to: U.S. provisional patent application Ser. No.61/525,168 filed Aug. 18, 2011, entitled “WALLET SERVICE ENROLLMENTPLATFORM APPARATUSES, METHODS AND SYSTEMS,” U.S. provisional patentapplication Ser. No. 61/537,421 filed Sep. 21, 2011, entitled “CONSUMERWALLET ENROLLMENT APPARATUSES, METHODS AND SYSTEMS,” U.S. provisionalpatent application Ser. No. 61/588,620 filed Jan. 19, 2012, entitled“CONSUMER WALLET ENROLLMENT APPARATUSES, METHODS AND SYSTEMS,” and U.S.provisional patent application Ser. No. 61/668,441 filed Jul. 5, 2012,entitled “REFERENCE TRANSACTION APPARATUSES, METHODS AND SYSTEMS.” Theentire contents of the aforementioned applications are expresslyincorporated by reference herein.

This application for letters patent disclosure document describesinventive aspects directed at various novel innovations (hereinafter“disclosure”) and contains material that is subject to copyright, maskwork, and/or other intellectual property protection. The respectiveowners of such intellectual property have no objection to the facsimilereproduction of the disclosure by anyone as it appears in publishedPatent Office file/records, but otherwise reserve all rights.

FIELD

The present innovations are directed generally to digital wallets andaccount management, and more particularly, to REMOTE DECOUPLEDAPPLICATION PERSISTENT STATE APPARATUSES, METHODS AND SYSTEMS.

BACKGROUND

Consumers using the World Wide Web browse product listings of merchantsand make purchases on selected products. Electronic data can be storedin computers and other storage devices for future access.

SUMMARY

In accordance with the teachings provided herein, systems, methods,non-transitory computer-readable medium, and apparatuses are disclosedfor operation upon data processing devices for processing digital wallettransaction-related persistent states, such as by: receiving, by use ofone or more processors, a wallet transaction-related persistent stateupdate request identifying a wallet user, wherein the wallettransaction-related persistent state update request includes walletpersistent state payload; storing, by use of the one or more processors,the wallet persistent state payload associated with the wallet user;receiving, by use of the one or more processors, a wallet persistentstate search criteria from the wallet user; providing, by use of the oneor more processors, the wallet persistent state search results to thewallet user; receiving, by use of the one or more processors, a walletpersistent state selection; and generating, by use of the one or moreprocessors, the wallet persistent state presentation based on the walletpersistent state selection.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate variousnon-limiting, example, innovative aspects in accordance with the presentdescriptions:

FIG. 1 shows a block diagram illustrating example cookie/states storagein some embodiments of the P-STATE;

FIG. 2 shows a block diagram illustrating example cookie/states storagedata flow in some embodiments of the P-STATE;

FIG. 3 shows a logic flow diagram illustrating example cookie/statesstorage component in some embodiments of the P-STATE;

FIGS. 4A-4C show user interfaces illustrating example cookie/statesstorage in some embodiments of the P-STATE;

FIG. 5 shows a block diagram illustrating example cookie states searchpresentation data flow in some embodiments of the P-STATE;

FIG. 6 shows a logic flow diagram illustrating example cookie statessearch presentation component in some embodiments of the P-STATE;

FIG. 7 shows a block diagram illustrating example cookie statesreload/recreate data flow in some embodiments of the P-STATE;

FIG. 8 shows a logic flow diagram illustrating example cookie statesreload/recreate component in some embodiments of the P-STATE;

FIG. 9 shows a block diagram illustrating embodiments of a P-STATEcontroller.

The leading number of each reference number within the drawingsindicates the figure in which that reference number is introduced and/ordetailed. As such, a detailed discussion of reference number 101 wouldbe found and/or introduced in FIG. 1. Reference number 201 is introducedin FIG. 2, etc.

DETAILED DESCRIPTION

Various embodiments of the P-STATE facilitate an enriched userexperience for digital wallet consumers and allow the consumers to storethe cookies and the states of their browsing and purchasing history withtheir digital wallet. In some embodiments, the digital wallet serverserves as a cloud based storage to the merchant so that the walletconsumers may retrieve any states they had in the past with thismerchant. In some embodiments, the cookie that the wallet stores mayhave multiple states and the consumer may choose go to any random stateand view the page. In some embodiments, because the cookies and statesare stored with the digital wallet server, it may be shared acrossplatform. For example, a consumer is at the kiosk at a merchant physicalstore and desires to purchase the items he looked for last night on thismerchant's website. The P-STATE may identify the consumer's digitalwallet and bring the items up at the kiosk. For another example, aconsumer is at a airplane and desires to watch the movie he purchasedbefore at home. The P-STATE may retrieve his prior purchase cookies andrecognize that he has already paid for that (although with anotherdevice) and provide the movie to him.

P-STATE

FIG. 1 shows a block diagram illustrating example cookie/states storagein some embodiments of the P-STATE. One possible cookie state 101 mayinclude a timestamp of when the state takes place 103, the merchant 105,the shopping cart status 107, the shipper 109, the offer 111, thepayment method 113, the checkout status 115, the search criteria (e.g.,T-shirt) 117, the search results list 119, the purchase status 121, theplatform the consumer is using (e.g., iphone, Android, merchant kiosk,point of sale, etc.) 123. The timestamp may be in the format of2005-02-03. The merchant of the order may be e-commerce sites such asAmazon. The search criteria may be the name of the product of interest,such as T-shirt. Another possible cookie state 125 may be the webpageproviding the search results related to the search criteria (e.g.,T-shirt) to the consumer. In some embodiments, it may also have thetimestamp, merchant, shopping cart, shipper, offer, payment method,checkout status, purchase status, and order platform. Meanwhile, it mayhave an empty search criteria field 129, and some products in the searchresults list, such as blue T-shirt, pink T-shirt, and so forth. Thereason may be that the search criteria may have been processed by thesystem and search results may have been generated. The consumer maychoose to add one of the products 9 e.g., blue T-shirt) from the searchresults into the cart. In another possible cookie state 133, thetimestamp, merchant, shopping cart, shipper, offer, payment method,search criteria, search results list, purchase status, and orderplatform may be the same as the previous cookie state. Meanwhile, itscheckout status may include one or more items, the home address, paymentmethod, and a link to the payment processing component. All possiblecookie and states may be stored 137 to the cookies database 139. Forexample, the P-STATE server may issue PHP/SQL commands similar to theexample listing below to store the cookies data 137 in a database:

<?PHP header(′Content-Type: text/plain′); mysql_connect(″254.92.185.103”,$DBserver,$password); // access database servermysql_select(″CookieStates.SQL″); // select database to appendmysql_query(“INSERT INTO CookieStatesTable (state_session_IDcookie_session_ID timestamp merchant shopping_cart shipper offerpayment_method checkout search search_results purchase platform) VALUES($state_session_ID $cookie_session_ID timestamp( ) $merchant$shopping_cart $shipper $offer $payment_method $checkout $search$search_results $purchase $platform”); // add data to table in databasemysql_close (″CookieStates.SQL″); // close connection to database ?>

In some embodiments, a cookie may have multiple states. In someembodiments, after the consumer places an order or finishes browsingwith this merchant, multiple states may be combined to one cookie.

FIG. 2 shows a block diagram illustrating example cookie/states storagedata flow in some embodiments of the P-STATE. A user 201 may submit thepurchase action input 211 to the client device 202. The purchase actioninput may include search, add to cart, pay and so forth. After receivingthe purchase action input, the client device may perform the requestedpurchase action and generate cookies 215. Then the client device maystore the cookie states 220 to the client cookie database 207. Anexample of the cookie state structure is discussed in message 230.Examples of PHP/SQL commands to store 220 may be similar to example 137.Following that the client device may update the wallet determination 225and determine how often the P-STATE server (e.g, wallet server) may needto be updated with the cookies. If the P-STATE server needs updating,then the client device may send the cookie states update package 230 tothe P-State server 205. An example cookies/states update packagesubstantially in the form of a HTTP(S) POST message 230 includingXML-formatted data, is provided below:

POST /updateacookiestates.php HTTP/1.1 Host: www.P-STATE.comContent-Type: Application/XML Content-Length: 667 <?XML version = “1.0”encoding = “UTF-8”?> <cookie_states_update_package>   <update_timestamp>2010-05-06 05:00</update_timestamp>   <last_update_timestamp>2010-05-05 05:00</last_update_timestamp>   <wallet_id>joesmith@gmail.com</wallet_id>   <cookie_session_ID>123adg      <state_session_ID>1       <timestamp>2010-05-05-09:12</timestamp>       <merchant_id>A12345</merchant_id>       <merchant>Amazon</merchant>       <merchant_session_id>vme0345</merchant_session_id>   <merchant_connection_server>159.2.8.45</merchant_connection_server>       <shopping_cart></shopping_cart>        <shipper></shipper>       <offer></offer>        <payment_method></payment_method>       <checkout> </checkout>        <search>T-shirt</search>       <search_results></search_results>        <purchase></purchase>       <platform></platform>      </state_session_ID>     <state_session_ID>2        <timestamp>2010-05-05-09:30</timestamp>       <merchant_id>A12345</merchant_id>       <merchant>Amazon</merchant>       <merchant_session_id>vme0345</merchant_session_id>   <merchant_connection_server>159.2.8.45</merchant_connection_server>       <shopping_cart></shopping_cart>        <shipper></shipper>       <offer></offer>        <payment_method></payment_method>       <checkout></checkout>        <search>T-shirt</search>       <search_results>1 Blue T-shirt, 2. Pink T- shirt</search_results>        <purchase></purchase>        <platform></platform>     </state_session_ID>      <state_session_ID>3       <timestamp>2010-05-05-09:40</timestamp>       <merchant_id>A12345</merchant_id>       <merchant>Amazon</merchant>       <merchant_session_id>vme0345</merchant _session_id>   <merchant_connection_server>159.2.8.45</merchant_connection_server>       <shopping_cart></shopping_cart>        <shipper></shipper>       <offer></offer>        <payment_method> Visa1234</payment_method>        <checkout>1. Blue T-shirt, 2. Camera Total$320 Address : 123 peace st. New York NY</checkout>       <search>T-shirt</search>        <search_results></search_results>       <purchase></purchase>        <platform></platform>     </state_session_ID>    </cookie_session_ID>   <cookie_session_ID>523adg      <state_session_ID>1       <timestamp>2011-05-05-09:12</timestamp>       <merchant_id>B12345</merchant_id>       <merchant>Bestbuy</merchant>       <merchant_session_id>vme1345</merchant_session_id>   <merchant_connection_server>259.2.8.45</merchant_connection_server>       <shopping_cart>Computer XXXX</shopping_cart>       <shipper>UPS</shipper>        <offer></offer>       <payment_method></payment_method>        <checkout> </checkout>       <search></search>        <search_results></search_results>       <purchase></purchase>        <platform>iphone</platform>     </state_session_ID>      <state_session_ID>2       <timestamp>2011-05-05-10:30</timestamp>       <merchant_id>B12345</merchant_id>       <merchant>Bestbuy</merchant>       <merchant_session_id>vme1345</merchant_session_id>   <merchant_connection_server>259.2.8.45</merchant_connection_server>       <shopping_cart>Computer XXXX</shopping_cart>       <shipper>UPS</shipper>        <offer>20% off</offer>       <payment_method></payment_method>        <checkout></checkout>       <search> </search>        <search_results></search_results>       <purchase></purchase>        <platform> iphone </platform>     </state_session_ID>    </cookie_session_ID></cookie_states_update_package>

After receiving the cookie states update package the P-State server mayupdate the cookie states 234. Then the P-State server may store thecookie states 240 into the P-State cookies database 209. Examples ofPHP/SQL commands to store 240 may be similar to example 137.

FIG. 3 shows a logic flow diagram illustrating example cookie/statesstorage component in some embodiments of the P-STATE. In someembodiments, the client may receive purchase action input, such assearch, add to cart, and so forth 311. Then the client may determinewhether the input includes a new merchant 313. If it does not include anew merchant, then the client may determine whether the transaction iscomplete 315. In some embodiments, it may determine whether a previoustransaction is complete. If the transaction is not complete, then theclient may determine if it is the first transaction 317. If the inputincludes a new merchant, or the transaction is complete, or it is thefirst transaction, then the client may set a new cookie flag 319. Afterthat the client may create a new cookie 321. The client may also set thecookie flag to complete and store the cookie on the device 329. Then theclient may create a new cookie state 325. After that and also if it doesnot involve a first transaction with the merchant 317, for each actionthat is queued 327, the client may create a new cookie state 325 andperform the received purchase action 323. Following that the client maystore the cookie states to the client cookies database with performedaction state information 331. Then the client may determine whetherthere is a wallet update quantum 333. If there is a wallet updatequantum, then the client may update the wallet determination, such as toupdate every 5 minutes, or one hour, or 3 days, and so forth 335. Afterthat the client may send cookie sates update package to the P-Stateserver 337. Then the P-State server may update the cookie states 341.After that the P-State server may store the updated cookie states to theP-State cookies database 343. If ted is not a wallet update quantum,then the client may determine whether there is a next queued action 339.If there is a next queued action, then the client may receive purchaseadditional action input.

FIGS. 4A-4C show user interfaces illustrating example cookie/statesstorage in some embodiments of the P-STATE. Referring to FIG. 4A, insome embodiments, cookies and states (cookies and states may be referredto cookie states, cookies, or states in some instances) may be viewed ina timeline fashion. 405, 407, 409 are different cookie states and whenthe mouse lies on one state, a preview of this state may be seen 405.Cookies on the right 401 have a newer timestamp than the cookies on theleft 403. Also a list of the cookies with file information may be shownunderneath 411. In the preview window 405, you may choose differentinformation to show. If you choose to view cart 413, you may see themerchant name, session id, timestamp, and a list of products in thecart. You may also search 415 in the cookies, view file info 423,preview the cookie 421, reload the cookie 419, and recreate the cookie417. In some embodiments, reloading the cookie means the merchant stillhas the cookie loaded. The merchant may send the payload information andconsumer's client device may load the cookie and generate for webpage orapp's display. In some embodiments, recreating the cookie means themerchant may not have the cookie loaded. Based on the payload info inthe stored cookie, the merchant may recreate the cookie and send to theconsumer. The reloading and recreating features are discussed in moredetails in FIGS. 7 and 8.

Referring to FIG. 4B, in some embodiments, cookies and states aresearchable. You may put in a search term 431, for example boot, theP_STATE may return you the cookies and states with “boot” in it 437.

Referring to FIG. 4C, in some embodiments, consumer may also view thecookies in a list view 451. Timestamp 455, product 457, price 459,merchant 461, platform 463, coupons 465, shippers 467, payment method,and other information may be shown. For some products, consumers mayview it in different platforms (for example, iPad 477, and merchantkiosk 479). In some embodiments, the cookies and states are searchable453. Users may choose different categories to search.

FIG. 5 shows a block diagram illustrating example cookie states searchpresentation data flow in some embodiments of the P-STATE. In someembodiments, a user 501 may submit the cookie states search criteriainput 511 to the client device 502. After receiving the search criteriainput, the client device may look up cookie state or states associatedwith the search criteria 515. After that it may generate a cookie statespresentation 520. Alternatively the client device may submit a cookiestates search request with search criteria 530 to the P-State server505. An example cookie states search request substantially in the formof a HTTP(S) POST message 530 including XML-formatted data, is providedbelow:

POST /cookiestatessearch.php HTTP/1.1 Host: www.P-STATE.comContent-Type: Application/XML Content-Length: 667 <?XML version = “1.0”encoding = “UTF-8”?> <cookie_states_search_request>   <wallet_id>joesmith@gmail.com</wallet_id>   <wallet_digital_certificate>****</wallet_digital_certificate>   <search_target>cookies</search_target>   <search_criteria>boots</search_criteria>   <search_period_from>2005-01-03</search_period_from>   <search_period_to>2006-01-03</search_period_to></cookie_states_search_request>

Then the P-State server may look up the cookie state or statesassociated with the search criteria 535. After that the P-State servermay send the cookie states search results 540 back to the client device.An example cookie states search results substantially in the form of aHTTP(S) PUSH message 540 including XML-formatted data, is providedbelow:

PUSH /cookiestatessearchresults.php HTTP/ 1.1 Host : www.P-STATE.comContent-Type: Application/XML Content-Length: 667 <?XML version = “1.0”encoding = “UTF-8”?> <cookie_states_search_results>   <wallet_id>joesmith@gmail.com</wallet_id>   <cookie_session_ID>123adg      <state_session_ID>3       <timestamp>2010-05-05-09:40</timestamp>       <merchant_id>A12345</merchant_id>       <merchant>Amazon</merchant>        <merchant_session_id>vme0345       </merchant_session_id>    <merchant_connection_server>159.2.8.45   </merchant_connection_server>        <shopping_cart></shopping_cart>       <shipper></shipper>        <offer></offer>       <payment_method> Visa 1234</payment_method>        <checkout>1.baby boots 2. books Total $320 Address: 123 peace st. New YorkNY</checkout>        <search></search>        <search_results></search_results>        <purchase></purchase>       <platform></platform>      </state_session_ID>   </cookie_session_ID>    <cookie_session_ID>523adg     <state_session_ID>1        <timestamp>2011-05-05-09:40</timestamp>       <merchant_id>M12345</merchant_id>       <merchant>Macy's</merchant>        <merchant_session_id>vme3345       </merchant_session_id>    <merchant_connection_server>159.2.8.45   </merchant_connection_server>        <shopping_cart></shopping_cart>       <shipper></shipper>        <offer></offer>       <payment_method> Visa 1234</payment_method>        <checkout>1.leather boots 2. computer Total $920 Address: 123 peace st. New YorkNY</checkout>        <search> </search>        <search_results></search_results>        <purchase></purchase>       <platform></platform>      </state_session_ID>   </cookie_session_ID>  </cookie_states_search_results>

The client device then may generate the cookie states presentation. Thenthe client device may display the results 525 to the user.

FIG. 6 shows a logic flow diagram illustrating example cookie statessearch presentation component in some embodiments of the P-STATE. Theclient may receive cookie states search criteria input 601. After thatthe client may look up cookie states associated with the search criteria605. Then the client may determine whether the cookies are found 607. Ifthe cookies are found, the client may load the cookie stats 609. If thecookies are not found, the client may send the cookie states searchrequest with the search criteria to the P-State server 615. Followingthat the P-State server may look up the cookie state or statesassociated with the search criteria 620. Then the P-State server maysend the cookie states search results to the client 625. After theclient loads the cookie states or the P-State server sends the cookiestates search results to the client, the client may generate cookiestates presentation 630.

FIG. 7 shows a block diagram illustrating example cookie statesreload/recreate data flow in some embodiments of the P-STATE. In someembodiments, the user may submit the cookie state(s) selection input 711to the client device 702. Then the client device may determine theplatform that is used, such as webpage, mobile app, and so forth, andload the cookies 715. After that the client device may reload orrecreate the cookie state request message, such as payload cookie andstates 720. An example reload/recreate cookie state requestsubstantially in the form of a HTTP(S) POST message 720 includingXML-formatted data, is provided below:

POST /reloadrecreatecookiestaterequest.php HTTP/1.1 Host:www.P-STATE.com Content-Type: Application/XML Content-Length: 667 <?XMLversion = “1.0” encoding = “UTF-8”?><reload_recreate_cookie_state_request>   <merchant_id>A12345</merchant_id>   <search_target>cookies</search_target>    <search_criteria>     <cookie_session_ID>123adg</cookie_session_ID>1     <state_session_ID>3</state_session_ID>    </search_criteria>   <search_period_from>2005-01-03</search_period_from>   <search_period_to>2006-01-03</search_period_to></reload_recreate_cookie_state_request>

Then the merchant server 705 may determine if the selected cookie stateis still loaded 725. Then the merchant server may load the selectedcookie state 730 and send the reloaded cookie state response back toclient, with info, for example, the webpage served or the mobileapplication payload 740. An example reload (or recreate) cookie stateresponse substantially in the form of a HTTP(S) PUSH message 740 (or745) including XML-formatted data, is provided below:

PUSH /reloadrecreatecookiestateresposne.php HTTP/1.1 Host:www.P-STATE.com Content-Type: Application/XML Content-Length: 667 <?XMLversion = “1.0” encoding = “UTF-8“?><reload_recreate_cookie_state_response>   <state_on_server_status>reloaded</state_on_server_status>//Alternatively, the state_on_server_status may also be recreated   <cookie_session_ID>123adg      <state_session_ID>3       <timestamp>2010-05-05-09:40</timestamp>       <merchant_id>A12345</merchant_id>       <merchant>Amazon</merchant>        <merchant_session_id>vme0345       </merchant_session_id>    <merchant_connection_server>159.2.8.45   </merchant_connection_server>        <shopping_cart></shopping_cart>       <shipper></shipper>        <offer></offer>       <payment_method> Visa 1234</payment_method>        <checkout>1.baby boots 2. books Total $320 Address: 123 peace st. New YorkNY</checkout>        <search></search>        <search_results></search_results>        <purchase></purchase>       <platform></platform>      </state_session_ID>   </cookie_session_ID> </reload_recreate_cookie_state_response>

The client may launch target for executing response payload, forexample, open browser or application, and load payload in target 750 fordisplay to the user 760. In an alternative embodiment, if the merchantserver do not have the selected cookie loaded 725, the merchant servermay recreate selected cookie state with payload cookie states (e.g.,load cart, search, shipping, pay, etc.) 735 and send it back to theclient 745. In another alternative embodiment, the merchant or theclient may request the selected cookie from the P-STATE server.

FIG. 8 shows a logic flow diagram illustrating example cookie statesreload/recreate component in some embodiments of the P-STATE. In someembodiments, the client may receive a cookie state selection input fromthe consumer 801. The client may then determine what platform was usedto send the input (e.g., webpage, mobile device application, etc.). Theclient may then generate and send a reload/recreate cookie statesrequest 805 to the merchant server 810. The merchant server maydetermine if selected cookie sate is till loaded on the merchant server815. If the cookie state is still loaded 822, the merchant server mayload selected cookie state and sends reload cookie state response to theclient 825. The response may also include a webpage server orapplication payload 830. Upon receiving the reload cookie stateresponse, the client may launch a target for executing response payload(e.g., open a browser, a mobile device application) and load payload intarget for display to the user 835. In some embodiments, if the cookieis no longer loaded at the merchant server 820, in an alternativeembodiment, the merchant server may determine if the session can berecreated 840. If the session can be recreated, the merchant server mayrecreate selected cookie state with actions such as loading card,searching, adding shipping, etc. 855. The merchant server may then sendrecreate confirmation response message with webpage served orapplication payload to the client 860. The client may then laugh targetand load payload in target 835. Alternatively, if the session can not berecreated 840 at the merchant server, the merchant may send a loadcookie state request to the P-STATE server 845 and retrieve cookiestates from the P-STATE server. Once the merchant receives cookie statesfrom the P-STATE server 855, the merchant may recreate selected cookiestate and send to client to load in target 835

P-STATE Controller

FIG. 9 shows a block diagram illustrating embodiments of a P-STATEcontroller. In this embodiment, the P-STATE controller 901 may serve toaggregate, process, store, search, serve, identify, instruct, generate,match, and/or facilitate interactions with a computer through variousbi-directional linking technologies, and/or other related data.

Typically, users, which may be people and/or other systems, may engageinformation technology systems (e.g., computers) to facilitateinformation processing. In turn, computers employ processors to processinformation; such processors 903 may be referred to as centralprocessing units (CPU). One form of processor is referred to as amicroprocessor. CPUs use communicative circuits to pass binary encodedsignals acting as instructions to enable various operations. Theseinstructions may be operational and/or data instructions containingand/or referencing other instructions and data in various processoraccessible and operable areas of memory 929 (e.g., registers, cachememory, random access memory, etc.). Such communicative instructions maybe stored and/or transmitted in batches (e.g., batches of instructions)as programs and/or data components to facilitate desired operations.These stored instruction codes, e.g., programs, may engage the CPUcircuit components and other motherboard and/or system components toperform desired operations. One type of program is a computer operatingsystem, which, may be executed by CPU on a computer; the operatingsystem enables and facilitates users to access and operate computerinformation technology and resources. Some resources that may beemployed in information technology systems include: input and outputmechanisms through which data may pass into and out of a computer;memory storage into which data may be saved; and processors by whichinformation may be processed. These information technology systems maybe used to collect data for later retrieval, analysis, and manipulation,which may be facilitated through a database program. These informationtechnology systems provide interfaces that allow users to access andoperate various system components.

In one embodiment, the P-STATE controller 901 may be connected to and/orcommunicate with entities such as, but not limited to: one or more usersfrom user input devices 911; peripheral devices 912; an optionalcryptographic processor device 928; and/or a communications network 913.

Networks are commonly thought to comprise the interconnection andinteroperation of clients, servers, and intermediary nodes in a graphtopology. It should be noted that the term “server” as used throughoutthis application refers generally to a computer, other device, program,or combination thereof that processes and responds to the requests ofremote users across a communications network. Servers serve theirinformation to requesting “clients.” The term “client” as used hereinrefers generally to a computer, program, other device, user and/orcombination thereof that is capable of processing and making requestsand obtaining and processing any responses from servers across acommunications network. A computer, other device, program, orcombination thereof that facilitates, processes information andrequests, and/or furthers the passage of information from a source userto a destination user is commonly referred to as a “node.” Networks aregenerally thought to facilitate the transfer of information from sourcepoints to destinations. A node specifically tasked with furthering thepassage of information from a source to a destination is commonly calleda “router.” There are many forms of networks such as Local Area Networks(LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks(WLANs), etc. For example, the Internet is generally accepted as beingan interconnection of a multitude of networks whereby remote clients andservers may access and interoperate with one another.

The P-STATE controller 901 may be based on computer systems that maycomprise, but are not limited to, components such as: a computersystemization 902 connected to memory 929.

Computer Systemization

A computer systemization 902 may comprise a clock 930, centralprocessing unit (“CPU(s)” and/or “processor(s)” (these terms are usedinterchangeable throughout the disclosure unless noted to the contrary))903, a memory 929 (e.g., a read only memory (ROM) 906, a random accessmemory (RAM) 905, etc.), and/or an interface bus 907, and mostfrequently, although not necessarily, are all interconnected and/orcommunicating through a system bus 904 on one or more (mother) board(s)902 having conductive and/or otherwise transportive circuit pathwaysthrough which instructions (e.g., binary encoded signals) may travel toeffectuate communications, operations, storage, etc. The computersystemization may be connected to a power source 986; e.g., optionallythe power source may be internal. Optionally, a cryptographic processor926 and/or transceivers (e.g., ICs) 974 may be connected to the systembus. In another embodiment, the cryptographic processor and/ortransceivers may be connected as either internal and/or externalperipheral devices 912 via the interface bus I/O. In turn, thetransceivers may be connected to antenna(s) 975, thereby effectuatingwireless transmission and reception of various communication and/orsensor protocols; for example the antenna(s) may connect to: a TexasInstruments WiLink WL1283 transceiver chip (e.g., providing 802.11n,Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowingP-STATE controller to determine its location)); Broadcom BCM4329FKUBGtransceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.);a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an InfineonTechnologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPAcommunications); and/or the like. The system clock typically has acrystal oscillator and generates a base signal through the computersystemization's circuit pathways. The clock is typically coupled to thesystem bus and various clock multipliers that will increase or decreasethe base operating frequency for other components interconnected in thecomputer systemization. The clock and various components in a computersystemization drive signals embodying information throughout the system.Such transmission and reception of instructions embodying informationthroughout a computer systemization may be commonly referred to ascommunications. These communicative instructions may further betransmitted, received, and the cause of return and/or replycommunications beyond the instant computer systemization to:communications networks, input devices, other computer systemizations,peripheral devices, and/or the like. It should be understood that inalternative embodiments, any of the above components may be connecteddirectly to one another, connected to the CPU, and/or organized innumerous variations employed as exemplified by various computer systems.

The CPU comprises at least one high-speed data processor adequate toexecute program components for executing user and/or system-generatedrequests. Often, the processors themselves will incorporate variousspecialized processing units, such as, but not limited to: integratedsystem (bus) controllers, memory management control units, floatingpoint units, and even specialized processing sub-units like graphicsprocessing units, digital signal processing units, and/or the like.Additionally, processors may include internal fast access addressablememory, and be capable of mapping and addressing memory 929 beyond theprocessor itself; internal memory may include, but is not limited to:fast registers, various levels of cache memory (e.g., level 1, 2, 3,etc.), RAM, etc. The processor may access this memory through the use ofa memory address space that is accessible via instruction address, whichthe processor can construct and decode allowing it to access a circuitpath to a specific memory address space having a memory state. The CPUmay be a microprocessor such as: AMD's Athlon, Duron and/or Opteron;ARM's application, embedded and secure processors; IBM and/or Motorola'sDragonBall and PowerPC; IBM's and Sony's Cell processor; Intel'sCeleron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or thelike processor(s). The CPU interacts with memory through instructionpassing through conductive and/or transportive conduits (e.g., (printed)electronic and/or optic circuits) to execute stored instructions (i.e.,program code) according to conventional data processing techniques. Suchinstruction passing facilitates communication within the P-STATEcontroller and beyond through various interfaces. Should processingrequirements dictate a greater amount speed and/or capacity, distributedprocessors (e.g., Distributed P-STATE), mainframe, multi-core, parallel,and/or super-computer architectures may similarly be employed.Alternatively, should deployment requirements dictate greaterportability, smaller Personal Digital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the P-STATE maybe achieved by implementing a microcontroller such as CAST's R8051XC2microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or thelike. Also, to implement certain features of the P-STATE, some featureimplementations may rely on embedded components, such as:Application-Specific Integrated Circuit (“ASIC”), Digital SignalProcessing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or thelike embedded technology. For example, any of the P-STATE componentcollection (distributed or otherwise) and/or features may be implementedvia the microprocessor and/or via embedded components; e.g., via ASIC,coprocessor, DSP, FPGA, and/or the like. Alternately, someimplementations of the P-STATE may be implemented with embeddedcomponents that are configured and used to achieve a variety of featuresor signal processing.

Depending on the particular implementation, the embedded components mayinclude software solutions, hardware solutions, and/or some combinationof both hardware/software solutions. For example, P-STATE featuresdiscussed herein may be achieved through implementing FPGAs, which are asemiconductor devices containing programmable logic components called“logic blocks”, and programmable interconnects, such as the highperformance FPGA Virtex series and/or the low cost Spartan seriesmanufactured by Xilinx. Logic blocks and interconnects can be programmedby the customer or designer, after the FPGA is manufactured, toimplement any of the P-STATE features. A hierarchy of programmableinterconnects allow logic blocks to be interconnected as needed by theP-STATE system designer/administrator, somewhat like a one-chipprogrammable breadboard. An FPGA's logic blocks can be programmed toperform the operation of basic logic gates such as AND, and XOR, or morecomplex combinational operators such as decoders or mathematicaloperations. In most FPGAs, the logic blocks also include memoryelements, which may be circuit flip-flops or more complete blocks ofmemory. In some circumstances, the P-STATE may be developed on regularFPGAs and then migrated into a fixed version that more resembles ASICimplementations. Alternate or coordinating implementations may migrateP-STATE controller features to a final ASIC instead of or in addition toFPGAs. Depending on the implementation all of the aforementionedembedded components and microprocessors may be considered the “CPU”and/or “processor” for the P-STATE.

Power Source

The power source 986 may be of any standard form for powering smallelectronic circuit board devices such as the following power cells:alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium,solar cells, and/or the like. Other types of AC or DC power sources maybe used as well. In the case of solar cells, in one embodiment, the caseprovides an aperture through which the solar cell may capture photonicenergy. The power cell 986 is connected to at least one of theinterconnected subsequent components of the P-STATE thereby providing anelectric current to all subsequent components. In one example, the powersource 986 is connected to the system bus component 904. In analternative embodiment, an outside power source 986 is provided througha connection across the I/O 908 interface. For example, a USB and/orIEEE 1394 connection carries both data and power across the connectionand is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 907 may accept, connect, and/or communicate to anumber of interface adapters, conventionally although not necessarily inthe form of adapter cards, such as but not limited to: input outputinterfaces (I/O) 908, storage interfaces 909, network interfaces 910,and/or the like. Optionally, cryptographic processor interfaces 927similarly may be connected to the interface bus. The interface busprovides for the communications of interface adapters with one anotheras well as with other components of the computer systemization.Interface adapters are adapted for a compatible interface bus. Interfaceadapters conventionally connect to the interface bus via a slotarchitecture. Conventional slot architectures may be employed, such as,but not limited to: Accelerated Graphics Port (AGP), Card Bus,(Extended) Industry Standard Architecture ((E)ISA), Micro ChannelArchitecture (MCA), NuBus, Peripheral Component Interconnect (Extended)(PCI(X)), PCI Express, Personal Computer Memory Card InternationalAssociation (PCMCIA), and/or the like.

Storage interfaces 909 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices914, removable disc devices, and/or the like. Storage interfaces mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),Institute of Electrical and Electronics Engineers (IEEE) 1394, fiberchannel, Small Computer Systems Interface (SCSI), Universal Serial Bus(USB), and/or the like.

Network interfaces 910 may accept, communicate, and/or connect to acommunications network 913. Through a communications network 913, theP-STATE controller is accessible through remote clients 933 b (e.g.,computers with web browsers) by users 933 a. Network interfaces mayemploy connection protocols such as, but not limited to: direct connect,Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or thelike), Token Ring, wireless connection such as IEEE 802.11a-x, and/orthe like. Should processing requirements dictate a greater amount speedand/or capacity, distributed network controllers (e.g., DistributedP-STATE), architectures may similarly be employed to pool, load balance,and/or otherwise increase the communicative bandwidth required by theP-STATE controller. A communications network may be any one and/or thecombination of the following: a direct interconnection; the Internet; aLocal Area Network (LAN); a Metropolitan Area Network (MAN); anOperating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a Wireless ApplicationProtocol (WAP), I-mode, and/or the like); and/or the like. A networkinterface may be regarded as a specialized form of an input outputinterface. Further, multiple network interfaces 910 may be used toengage with various communications network types 913. For example,multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 908 may accept, communicate, and/orconnect to user input devices 911, peripheral devices 912, cryptographicprocessor devices 928, and/or the like. I/O may employ connectionprotocols such as, but not limited to: audio: analog, digital, monaural,RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE1394a-b, serial, universal serial bus (USB); infrared; joystick;keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface:Apple Desktop Connector (ADC), BNC, coaxial, component, composite,digital, Digital Visual Interface (DVI), high-definition multimediainterface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like;wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., codedivision multiple access (CDMA), high speed packet access (HSPA(+)),high-speed downlink packet access (HSDPA), global system for mobilecommunications (GSM), long term evolution (LTE), WiMax, etc.); and/orthe like. One typical output device may include a video display, whichtypically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display(LCD) based monitor with an interface (e.g., DVI circuitry and cable)that accepts signals from a video interface, may be used. The videointerface composites information generated by a computer systemizationand generates video signals based on the composited information in avideo memory frame. Another output device is a television set, whichaccepts signals from a video interface. Typically, the video interfaceprovides the composited video information through a video connectioninterface that accepts a video display interface (e.g., an RCA compositevideo connector accepting an RCA composite video cable; a DVI connectoraccepting a DVI display cable, etc.).

User input devices 911 often are a type of peripheral device 512 (seebelow) and may include: card readers, dongles, finger print readers,gloves, graphics tablets, joysticks, keyboards, microphones, mouse(mice), remote controls, retina readers, touch screens (e.g.,capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g.,accelerometers, ambient light, GPS, gyroscopes, proximity, etc.),styluses, and/or the like.

Peripheral devices 912 may be connected and/or communicate to I/O and/orother facilities of the like such as network interfaces, storageinterfaces, directly to the interface bus, system bus, the CPU, and/orthe like. Peripheral devices may be external, internal and/or part ofthe P-STATE controller. Peripheral devices may include: antenna, audiodevices (e.g., line-in, line-out, microphone input, speakers, etc.),cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copyprotection, ensuring secure transactions with a digital signature,and/or the like), external processors (for added capabilities; e.g.,crypto devices 528), force-feedback devices (e.g., vibrating motors),network interfaces, printers, scanners, storage devices, transceivers(e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors,etc.), video sources, visors, and/or the like. Peripheral devices ofteninclude types of input devices (e.g., cameras).

It should be noted that although user input devices and peripheraldevices may be employed, the P-STATE controller may be embodied as anembedded, dedicated, and/or monitor-less (i.e., headless) device,wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers,processors 926, interfaces 927, and/or devices 928 may be attached,and/or communicate with the P-STATE controller. A MC68HC16microcontroller, manufactured by Motorola Inc., may be used for and/orwithin cryptographic units. The MC68HC16 microcontroller utilizes a16-bit multiply-and-accumulate instruction in the 16 MHz configurationand requires less than one second to perform a 512-bit RSA private keyoperation. Cryptographic units support the authentication ofcommunications from interacting agents, as well as allowing foranonymous transactions. Cryptographic units may also be configured aspart of the CPU. Equivalent microcontrollers and/or processors may alsobe used. Other commercially available specialized cryptographicprocessors include: Broadcom's CryptoNetX and other Security Processors;nCipher's nShield; SafeNet's Luna PCI (e.g., 7100) series; SemaphoreCommunications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators(e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); ViaNano Processor (e.g., L2100, L2200, U2400) line, which is capable ofperforming 500+MB/s of cryptographic instructions; VLSI Technology's 33MHz 6868; and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor toaffect the storage and/or retrieval of information is regarded as memory929. However, memory is a fungible technology and resource, thus, anynumber of memory embodiments may be employed in lieu of or in concertwith one another. It is to be understood that the P-STATE controllerand/or a computer systemization may employ various forms of memory 929.For example, a computer systemization may be configured wherein theoperation of on-chip CPU memory (e.g., registers), RAM, ROM, and anyother storage devices are provided by a paper punch tape or paper punchcard mechanism; however, such an embodiment would result in an extremelyslow rate of operation. In a typical configuration, memory 929 willinclude ROM 906, RAM 905, and a storage device 914. A storage device 914may be any conventional computer system storage. Storage devices mayinclude a drum; a (fixed and/or removable) magnetic disk drive; amagneto-optical drive; an optical drive (i.e., Blueray, CDROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); anarray of devices (e.g., Redundant Array of Independent Disks (RAID));solid state memory devices (USB memory, solid state drives (SSD), etc.);other processor-readable storage mediums; and/or other devices of thelike. Thus, a computer systemization generally requires and makes use ofmemory.

Component Collection

The memory 929 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 915 (operating system); information server component(s) 916(information server); user interface component(s) 917 (user interface);Web browser component(s) 918 (Web browser); database(s) 919; mail servercomponent(s) 921; mail client component(s) 922; cryptographic servercomponent(s) 920 (cryptographic server); the P-STATE component(s) 935;cookie/states storage (“CSS”) component 941; cookie states searchpresentation (“CSSP”) component 942; and cookie/states reload/recreate(“CSRR”) component 943; and/or the like (i.e., collectively a componentcollection). These components may be stored and accessed from thestorage devices and/or from storage devices accessible through aninterface bus. Although non-conventional program components such asthose in the component collection, typically, are stored in a localstorage device 914, they may also be loaded and/or stored in memory suchas: peripheral devices, RAM, remote storage facilities through acommunications network, ROM, various forms of memory, and/or the like.

Operating System

The operating system component 915 is an executable program componentfacilitating the operation of the P-STATE controller. Typically, theoperating system facilitates access of I/O, network interfaces,peripheral devices, storage devices, and/or the like. The operatingsystem may be a highly fault tolerant, scalable, and secure system suchas: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix andUnix-like system distributions (such as AT&T's UNIX; Berkley SoftwareDistribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/orthe like; Linux distributions such as Red Hat, Ubuntu, and/or the like);and/or the like operating systems. However, more limited and/or lesssecure operating systems also may be employed such as Apple MacintoshOS, IBM OS/2, Microsoft DOS, Microsoft Windows2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/orthe like. An operating system may communicate to and/or with othercomponents in a component collection, including itself, and/or the like.Most frequently, the operating system communicates with other programcomponents, user interfaces, and/or the like. For example, the operatingsystem may contain, communicate, generate, obtain, and/or provideprogram component, system, user, and/or data communications, requests,and/or responses. The operating system, once executed by the CPU, mayenable the interaction with communications networks, data, I/O,peripheral devices, program components, memory, user input devices,and/or the like. The operating system may provide communicationsprotocols that allow the P-STATE controller to communicate with otherentities through a communications network 913. Various communicationprotocols may be used by the P-STATE controller as a subcarriertransport mechanism for interaction, such as, but not limited to:multicast, TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 916 is a stored program component thatis executed by a CPU. The information server may be a conventionalInternet information server such as, but not limited to Apache SoftwareFoundation's Apache, Microsoft's Internet Information Server, and/or thelike. The information server may allow for the execution of programcomponents through facilities such as Active Server Page (ASP), ActiveX,(ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface(CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH,Java, JavaScript, Practical Extraction Report Language (PERL), HypertextPre-Processor (PHP), pipes, Python, wireless application protocol (WAP),WebObjects, and/or the like. The information server may support securecommunications protocols such as, but not limited to, File TransferProtocol (FTP); HyperText Transfer Protocol (HTTP); Secure HypertextTransfer Protocol (HTTPS), Secure Socket Layer (SSL), messagingprotocols (e.g., America Online (AOL) Instant Messenger (AIM),Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), MicrosoftNetwork (MSN) Messenger Service, Presence and Instant Messaging Protocol(PRIM), Internet Engineering Task Force's (IETF's) Session InitiationProtocol (SIP), SIP for Instant Messaging and Presence LeveragingExtensions (SIMPLE), open XML-based Extensible Messaging and PresenceProtocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) InstantMessaging and Presence Service (IMPS)), Yahoo! Instant MessengerService, and/or the like. The information server provides results in theform of Web pages to Web browsers, and allows for the manipulatedgeneration of the Web pages through interaction with other programcomponents. After a Domain Name System (DNS) resolution portion of anHTTP request is resolved to a particular information server, theinformation server resolves requests for information at specifiedlocations on the P-STATE controller based on the remainder of the HTTPrequest. For example, a request such ashttp://123.124.125.126/myInformation.html might have the IP portion ofthe request “123.124.125.126” resolved by a DNS server to an informationserver at that IP address; that information server might in turn furtherparse the http request for the “/myInformation.html” portion of therequest and resolve it to a location in memory containing theinformation “myInformation.html.” Additionally, other informationserving protocols may be employed across various ports, e.g., FTPcommunications across port 21, and/or the like. An information servermay communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the information server communicates with the P-STATEdatabase 919, operating systems, other program components, userinterfaces, Web browsers, and/or the like.

Access to the P-STATE database may be achieved through a number ofdatabase bridge mechanisms such as through scripting languages asenumerated below (e.g., CGI) and through inter-application communicationchannels as enumerated below (e.g., CORBA, WebObjects, etc.). Any datarequests through a Web browser are parsed through the bridge mechanisminto appropriate grammars as required by the P-STATE. In one embodiment,the information server would provide a Web form accessible by a Webbrowser. Entries made into supplied fields in the Web form are tagged ashaving been entered into the particular fields, and parsed as such. Theentered terms are then passed along with the field tags, which act toinstruct the parser to generate queries directed to appropriate tablesand/or fields. In one embodiment, the parser may generate queries instandard SQL by instantiating a search string with the properjoin/select commands based on the tagged text entries, wherein theresulting command is provided over the bridge mechanism to the P-STATEas a query. Upon generating query results from the query, the resultsare passed over the bridge mechanism, and may be parsed for formattingand generation of a new results Web page by the bridge mechanism. Such anew results Web page is then provided to the information server, whichmay supply it to the requesting Web browser.

Also, an information server may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

User Interface

Computer interfaces in some respects are similar to automobile operationinterfaces. Automobile operation interface elements such as steeringwheels, gearshifts, and speedometers facilitate the access, operation,and display of automobile resources, and status. Computer interactioninterface elements such as check boxes, cursors, menus, scrollers, andwindows (collectively and commonly referred to as widgets) similarlyfacilitate the access, capabilities, operation, and display of data andcomputer hardware and operating system resources, and status. Operationinterfaces are commonly called user interfaces. Graphical userinterfaces (GUIs) such as the Apple Macintosh Operating System's Aqua,IBM's OS/2, Microsoft's Windows2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix'sX-Windows (e.g., which may include additional Unix graphic interfacelibraries and layers such as K Desktop Environment (KDE), mythTV and GNUNetwork Object Model Environment (GNOME)), web interface libraries(e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interfacelibraries such as, but not limited to, Dojo, jQuery(UI), MooTools,Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any ofwhich may be used and) provide a baseline and means of accessing anddisplaying information graphically to users.

A user interface component 917 is a stored program component that isexecuted by a CPU. The user interface may be a conventional graphic userinterface as provided by, with, and/or atop operating systems and/oroperating environments such as already discussed. The user interface mayallow for the display, execution, interaction, manipulation, and/oroperation of program components and/or system facilities through textualand/or graphical facilities. The user interface provides a facilitythrough which users may affect, interact, and/or operate a computersystem. A user interface may communicate to and/or with other componentsin a component collection, including itself, and/or facilities of thelike. Most frequently, the user interface communicates with operatingsystems, other program components, and/or the like. The user interfacemay contain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Web Browser

A Web browser component 918 is a stored program component that isexecuted by a CPU. The Web browser may be a conventional hypertextviewing application such as Microsoft Internet Explorer or NetscapeNavigator. Secure Web browsing may be supplied with 128bit (or greater)encryption by way of HTTPS, SSL, and/or the like. Web browsers allowingfor the execution of program components through facilities such asActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-inAPIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or thelike. Web browsers and like information access tools may be integratedinto PDAs, cellular telephones, and/or other mobile devices. A Webbrowser may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the Web browser communicates with information servers,operating systems, integrated program components (e.g., plug-ins),and/or the like; e.g., it may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses. Also, in place of a Webbrowser and information server, a combined application may be developedto perform similar operations of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the P-STATE enabled nodes. Thecombined application may be nugatory on systems employing standard Webbrowsers.

Mail Server

A mail server component 921 is a stored program component that isexecuted by a CPU 903. The mail server may be a conventional Internetmail server such as, but not limited to sendmail, Microsoft Exchange,and/or the like. The mail server may allow for the execution of programcomponents through facilities such as ASP, ActiveX, (ANSI) (Objective-)C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes,Python, WebObjects, and/or the like. The mail server may supportcommunications protocols such as, but not limited to: Internet messageaccess protocol (IMAP), Messaging Application Programming Interface(MAPI)/Microsoft Exchange, post office protocol (POP3), simple mailtransfer protocol (SMTP), and/or the like. The mail server can route,forward, and process incoming and outgoing mail messages that have beensent, relayed and/or otherwise traversing through and/or to the P-STATE.

Access to the P-STATE mail may be achieved through a number of APIsoffered by the individual Web server components and/or the operatingsystem.

Also, a mail server may contain, communicate, generate, obtain, and/orprovide program component, system, user, and/or data communications,requests, information, and/or responses.

Mail Client

A mail client component 922 is a stored program component that isexecuted by a CPU 903. The mail client may be a conventional mailviewing application such as Apple Mail, Microsoft Entourage, MicrosoftOutlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or thelike. Mail clients may support a number of transfer protocols, such as:IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, themail client communicates with mail servers, operating systems, othermail clients, and/or the like; e.g., it may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, information, and/or responses. Generally,the mail client provides a facility to compose and transmit electronicmail messages.

Cryptographic Server

A cryptographic server component 920 is a stored program component thatis executed by a CPU 903, cryptographic processor 926, cryptographicprocessor interface 927, cryptographic processor device 928, and/or thelike. Cryptographic processor interfaces will allow for expedition ofencryption and/or decryption requests by the cryptographic component;however, the cryptographic component, alternatively, may run on aconventional CPU. The cryptographic component allows for the encryptionand/or decryption of provided data. The cryptographic component allowsfor both symmetric and asymmetric (e.g., Pretty Good Protection (PGP))encryption and/or decryption. The cryptographic component may employcryptographic techniques such as, but not limited to: digitalcertificates (e.g., X.509 authentication framework), digital signatures,dual signatures, enveloping, password access protection, public keymanagement, and/or the like. The cryptographic component will facilitatenumerous (encryption and/or decryption) security protocols such as, butnot limited to: checksum, Data Encryption Standard (DES), EllipticalCurve Encryption (ECC), International Data Encryption Algorithm (IDEA),Message Digest 5 (MD5, which is a one way hash operation), passwords,Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption andauthentication system that uses an algorithm developed in 1977 by RonRivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA),Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS),and/or the like. Employing such encryption security protocols, theP-STATE may encrypt all incoming and/or outgoing communications and mayserve as node within a virtual private network (VPN) with a widercommunications network. The cryptographic component facilitates theprocess of “security authorization” whereby access to a resource isinhibited by a security protocol wherein the cryptographic componenteffects authorized access to the secured resource. In addition, thecryptographic component may provide unique identifiers of content, e.g.,employing and MD5 hash to obtain a unique signature for an digital audiofile. A cryptographic component may communicate to and/or with othercomponents in a component collection, including itself, and/orfacilities of the like. The cryptographic component supports encryptionschemes allowing for the secure transmission of information across acommunications network to enable the P-STATE component to engage insecure transactions if so desired. The cryptographic componentfacilitates the secure accessing of resources on the P-STATE andfacilitates the access of secured resources on remote systems; i.e., itmay act as a client and/or server of secured resources. Most frequently,the cryptographic component communicates with information servers,operating systems, other program components, and/or the like. Thecryptographic component may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

The P-State Database

The P-STATE database component 919 may be embodied in a database and itsstored data. The database is a stored program component, which isexecuted by the CPU; the stored program component portion configuringthe CPU to process the stored data. The database may be a conventional,fault tolerant, relational, scalable, secure database such as Oracle orSybase. Relational databases are an extension of a flat file. Relationaldatabases consist of a series of related tables. The tables areinterconnected via a key field. Use of the key field allows thecombination of the tables by indexing against the key field; i.e., thekey fields act as dimensional pivot points for combining informationfrom various tables. Relationships generally identify links maintainedbetween tables by matching primary keys. Primary keys represent fieldsthat uniquely identify the rows of a table in a relational database.More precisely, they uniquely identify rows of a table on the “one” sideof a one-to-many relationship.

Alternatively, the P-STATE database may be implemented using variousstandard data-structures, such as an array, hash, (linked) list, struct,structured text file (e.g., XML), table, and/or the like. Suchdata-structures may be stored in memory and/or in (structured) files. Inanother alternative, an object-oriented database may be used, such asFrontier, ObjectStore, Poet, Zope, and/or the like. Object databases caninclude a number of object collections that are grouped and/or linkedtogether by common attributes; they may be related to other objectcollections by some common attributes. Object-oriented databases performsimilarly to relational databases with the exception that objects arenot just pieces of data but may have other types of capabilitiesencapsulated within a given object. If the P-STATE database isimplemented as a data-structure, the use of the P-STATE database 919 maybe integrated into another component such as the P-STATE component 935.Also, the database may be implemented as a mix of data structures,objects, and relational structures. Databases may be consolidated and/ordistributed in countless variations through standard data processingtechniques. Portions of databases, e.g., tables, may be exported and/orimported and thus decentralized and/or integrated.

In one embodiment, the database component 919 includes several tables919 a-o. A user table 919 a includes fields such as, but not limited to:a user_ID, name, home_address, work_address, telephone_number, email,merchant_ID client_id, account_id, and/or the like. The user table maysupport and/or track multiple entity accounts on a P-STATE. Amerchant/service provider table 919 b includes fields such as, but notlimited to: merchant_ID, merchant_name, merchant_location,merchant_address, merchant_category_code, merchant_api_key,loyalty_program_ID and/or the like. A customer profile table 919 cincludes fields such as, but not limited to: user_ID, merchant_ID,payment_card_ID, preferred_payment_type, demographics,prefetch_preferences, and/or the like. A permissions table 919 dincludes fields such as, but not limited to: customer ID, transactionexecution authorization status, confirmation authorization status,billing authorization status, subscription payment authorization status,and/or the like. A payment card table 919 e includes fields such as, butnot limited to: payment_card_id, user_id, identifier, brand, expirationdate, spending limit, billing address, issuer, name, nick name, loyaltyprogram ID, and/or the like. A billing agreement table 919 f includesfields such as, but not limited to: customer_id, billing_id,billing_date, billing_amount_limit, confirmation_requirement,authentication_level, billing_authorization_status, and/or the like. Aredemption table 919 g includes fields such as, but not limited to:customer_id, loyalty_program_id, coupon_id, redemption_date,redemption_time, redemption_amount, redemption_type, transaction_id,and/or the like. A loyalty table 919 h includes fields such as, but notlimited to: loyalty program ID, rules, loyalty currency amount, loyaltyexpiry date, transaction ID, and/or the like. A coupons table 919 iincludes fields such as, but not limited to: coupon ID, coupon value,coupon accepted location, coupon expiry date, and/or the like. A wishlist table 919 j includes fields such as, but not limited to: wish listID, merchant ID, item ID, and/or the like. A shopping lists table 919 kincludes fields such as, but not limited to: shopping_lists_ID,merchant_ID, item_ID, transaction_ID, and/or the like. A storeinjections table 919 l includes fields such as, but not limited to:store_injection_id, merchant_id, item_id, and/or the like. A transactiontable 919 m includes fields such as, but not limited to: transaction_id,merchant_id, user_id, session_id, date, time, item_model, manufacturer,price, item_id, and/or the like. A products table 919 n includes fieldssuch as, but not limited to: product_id, merchant_id, item_id, and/orthe like. A cookie_states table 919 o includes fields such as, but notlimited to: cookie_states_id, cookie_session_id, states_session_id,merchant_id, timestamp, shopping_list_id, payment_method_id,payment_card_id, search, search_results, platform, checkout, shipper,offer, and/or the like.

An Account table 919 e includes fields such as, but not limited to:account_id, account_PAN, account_type, brand, expiration date, spendinglimit, billing address, issuer, name, nick name, loyalty program ID,and/or the like. A third parties table 919 f includes fields such as,but not limited to: 3^(rd)_parties_ID, 3^(rd)_parties_name,3^(rd)_parties_type, 3^(rd)_parties_location, 3^(rd)_parties_address,3^(rd)_parties_api_key, prefetch_request_id, user_id, merchant_id,security_credentials, and/or the like. A redemption table 919 g includesfields such as, but not limited to: customer ID, loyalty program ID,coupon ID, redemption date, redemption time, redemption amount,redemption type, transaction ID, and/or the like. A loyalty table 919 hincludes fields such as, but not limited to: loyalty program ID, rules,loyalty currency amount, loyalty expiry date, transaction ID, and/or thelike. A coupons table 919 i includes fields such as, but not limited to:coupon ID, coupon value, coupon accepted location, coupon expiry date,and/or the like. A wish list table 919 j includes fields such as, butnot limited to: wish list ID, merchant ID, item ID, and/or the like. Aplug-ins table 919 k includes fields such as, but not limited to:plug-in ID, plug-in provider ID (merchant ID, issuer ID, etc.), plug-intype, plug-in function, plug-in installation guide, plug-inauthorization, plug-in restrictions, and/or the like. A client cookiestable 919 l includes fields such as, but not limited to: clientcookie_id, session_ID, client_id, user_id, merchant_id, wallet_id,merchant_login, wallet_login, cookie_timestamp, cookie_address, and/orthe like. An account balance table 919 m includes fields such as, butnot limited to: user_ID, Account_ID, issuer, api key, balance amount,balance retrieval date/time, and/or the like. and/or the like. Apayments table 919 n includes fields such as, but not limited to:user_id, billing ID, billing date, billing amount, Account_ID,authentication level, and/or the like. A prefetch requests table 919 oincludes fields such as, but not limited to: prefetch_requests_id,user_id, client_id, 3^(rd)_parties_id, api_id, prefetch_info_type,prefetch_info_value, and/or the like.

In one embodiment, the P-STATE database may interact with other databasesystems. For example, employing a distributed database system, queriesand data access by search P-STATE component may treat the combination ofthe P-STATE database, an integrated data security layer database as asingle database entity.

In one embodiment, user programs may contain various user interfaceprimitives, which may serve to update the P-STATE. Also, variousaccounts may require custom database tables depending upon theenvironments and the types of clients the P-STATE may need to serve. Itshould be noted that any unique fields may be designated as a key fieldthroughout. In an alternative embodiment, these tables have beendecentralized into their own databases and their respective databasecontrollers (i.e., individual database controllers for each of the abovetables). Employing standard data processing techniques, one may furtherdistribute the databases over several computer systemizations and/orstorage devices. Similarly, configurations of the decentralized databasecontrollers may be varied by consolidating and/or distributing thevarious database components 919 a-o. The P-STATE may be configured tokeep track of various settings, inputs, and parameters via databasecontrollers.

The P-STATE database may communicate to and/or with other components ina component collection, including itself, and/or facilities of the like.Most frequently, the P-STATE database communicates with the P-STATEcomponent, other program components, and/or the like. The database maycontain, retain, and provide information regarding other nodes and data.

The P-STATEs

The P-STATE component 935 is a stored program component that is executedby a CPU. In one embodiment, the P-STATE component incorporates anyand/or all combinations of the aspects of the P-STATE that was discussedin the previous figures. As such, the P-STATE affects accessing,obtaining and the provision of information, services, transactions,and/or the like across various communications networks.

The P-STATE transforms inputs such as purchase action input (e.g., 211),cookie states search criteria input (e.g., 511), and cookie statesselection input (e.g., 711) via P-STATE components such as cookie/statesstorage (“CSS”) component 941; cookie states search presentation(“CSSP”) component 942; and cookie/states reload/recreate (“CSRR”)component 943, into cookie state presentation (e.g., 525, 760) outputs.

The P-STATE component enabling access of information between nodes maybe developed by employing standard development tools and languages suchas, but not limited to: Apache components, Assembly, ActiveX, binaryexecutables, (ANSI) (Objective-) C (++), C# and/or .NET, databaseadapters, CGI scripts, Java, JavaScript, mapping tools, procedural andobject oriented development tools, PERL, PHP, Python, shell scripts, SQLcommands, web application server extensions, web developmentenvironments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX &FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools;Prototype; script.aculo.us; Simple Object Access Protocol (SOAP);SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/orthe like. In one embodiment, the P-STATE server employs a cryptographicserver to encrypt and decrypt communications. The P-STATE component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, theP-STATE component communicates with the P-STATE database, operatingsystems, other program components, and/or the like. The P-STATE maycontain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Distributed P-STATEs

The structure and/or operation of any of the P-STATE node controllercomponents may be combined, consolidated, and/or distributed in anynumber of ways to facilitate development and/or deployment. Similarly,the component collection may be combined in any number of ways tofacilitate deployment and/or development. To accomplish this, one mayintegrate the components into a common code base or in a facility thatcan dynamically load the components on demand in an integrated fashion.

The component collection may be consolidated and/or distributed incountless variations through standard data processing and/or developmenttechniques. Multiple instances of any one of the program components inthe program component collection may be instantiated on a single node,and/or across numerous nodes to improve performance throughload-balancing and/or data-processing techniques. Furthermore, singleinstances may also be distributed across multiple controllers and/orstorage devices; e.g., databases. All program component instances andcontrollers working in concert may do so through standard dataprocessing communication techniques.

The configuration of the P-STATE controller will depend on the contextof system deployment. Factors such as, but not limited to, the budget,capacity, location, and/or use of the underlying hardware resources mayaffect deployment requirements and configuration. Regardless of if theconfiguration results in more consolidated and/or integrated programcomponents, results in a more distributed series of program components,and/or results in some combination between a consolidated anddistributed configuration, data may be communicated, obtained, and/orprovided. Instances of components consolidated into a common code basefrom the program component collection may communicate, obtain, and/orprovide data. This may be accomplished through intra-application dataprocessing communication techniques such as, but not limited to: datareferencing (e.g., pointers), internal messaging, object instancevariable communication, shared memory space, variable passing, and/orthe like.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other component components may be accomplishedthrough inter-application data processing communication techniques suchas, but not limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), Jini local and remote applicationprogram interfaces, JavaScript Object Notation (JSON), Remote MethodInvocation (RMI), SOAP, process pipes, shared files, and/or the like.Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar. A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of anHTTP post command, e.g.:

-   -   w3c-post http:// . . . Value1

where Value1 is discerned as being a parameter because “http://” is partof the grammar syntax, and what follows is considered part of the postvalue. Similarly, with such a grammar, a variable “Value1” may beinserted into an “http://” post command and then sent. The grammarsyntax itself may be presented as structured data that is interpretedand/or otherwise used to generate the parsing mechanism (e.g., a syntaxdescription text file as processed by lex, yacc, etc.). Also, once theparsing mechanism is generated and/or instantiated, it itself mayprocess and/or parse structured data such as, but not limited to:character (e.g., tab) delineated text, HTML, structured text streams,XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or readily available parsers (e.g., JSON, SOAP, and/orlike parsers) that may be employed to parse (e.g., communications) data.Further, the parsing grammar may be used beyond message parsing, but mayalso be used to parse: databases, data collections, data stores,structured data, and/or the like. Again, the desired configuration willdepend upon the context, environment, and requirements of systemdeployment.

For example, in some implementations, the P-STATE controller may beexecuting a PHP script implementing a Secure Sockets Layer (“SSL”)socket server via the information sherver, which listens to incomingcommunications on a server port to which a client may send data, e.g.,data encoded in JSON format. Upon identifying an incoming communication,the PHP script may read the incoming message from the client device,parse the received JSON-encoded text data to extract information fromthe JSON-encoded text data into PHP script variables, and store the data(e.g., client identifying information, etc.) and/or extractedinformation in a relational database accessible using the StructuredQuery Language (“SQL”). An exemplary listing, written substantially inthe form of PHP/SQL commands, to accept JSON-encoded input data from aclient device via a SSL connection, parse the data to extract variables,and store the data to a database, is provided below:

<?PHP header(′Content-Type: text/plain′); // set ip address and port tolisten to for incoming data $address = ‘192.168.0.100’; $port = 255; //create a server-side SSL socket, listen for/accept incomingcommunication $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); // read input datafrom client device in 1024 byte blocks until end of message do {   $input = “”;    $input = socket_read($client, 1024);    $data .=$input; } while($input != “”); // parse data to extract variables $obj =json_decode($data, true); // store input data in a databasemysql_connect(″201.408.185.132″,$DBserver,$password); // access databaseserver mysql_select(″CLIENT_DB.SQL″); // select database to appendmysql_query(“INSERT INTO UserTable (transmission) VALUES ($data)”); //add data to UserTable table in a CLIENT databasemysql_close(″CLIENT_DB.SQL″); // close connection to database ?>

Also, the following resources may be used to provide example embodimentsregarding SOAP parser implementation:

http://www.xav.com/perl/site/lib/SOAP/Parser.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htm

and other parser implementations:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htm

all of which are hereby expressly incorporated by reference.

In order to address various issues and advance the art, the entirety ofthis application for REMOTE DECOUPLED APPLICATION PERSISTENT STATEAPPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title,Headings, Field, Background, Summary, Brief Description of the Drawings,Detailed Description, Claims, Abstract, Figures, Appendices, andotherwise) shows, by way of illustration, various embodiments in whichthe claimed innovations may be practiced. The advantages and features ofthe application are of a representative sample of embodiments only, andare not exhaustive and/or exclusive. They are presented only to assistin understanding and teach the claimed principles. It should beunderstood that they are not representative of all claimed innovations.As such, certain aspects of the disclosure have not been discussedherein. That alternate embodiments may not have been presented for aspecific portion of the innovations or that further undescribedalternate embodiments may be available for a portion is not to beconsidered a disclaimer of those alternate embodiments. It will beappreciated that many of those undescribed embodiments incorporate thesame principles of the innovations and others are equivalent. Thus, itis to be understood that other embodiments may be utilized andfunctional, logical, operational, organizational, structural and/ortopological modifications may be made without departing from the scopeand/or spirit of the disclosure. As such, all examples and/orembodiments are deemed to be non-limiting throughout this disclosure.Also, no inference should be drawn regarding those embodiments discussedherein relative to those not discussed herein other than it is as suchfor purposes of reducing space and repetition. For instance, it is to beunderstood that the logical and/or topological structure of anycombination of any program components (a component collection), othercomponents and/or any present feature sets as described in the figuresand/or throughout are not limited to a fixed operating order and/orarrangement, but rather, any disclosed order is exemplary and allequivalents, regardless of order, are contemplated by the disclosure.Furthermore, it is to be understood that such features are not limitedto serial execution, but rather, any number of threads, processes,services, servers, and/or the like that may execute asynchronously,concurrently, in parallel, simultaneously, synchronously, and/or thelike are contemplated by the disclosure. As such, some of these featuresmay be mutually contradictory, in that they cannot be simultaneouslypresent in a single embodiment. Similarly, some features are applicableto one aspect of the innovations, and inapplicable to others. Inaddition, the disclosure includes other innovations not presentlyclaimed. Applicant reserves all rights in those presently unclaimedinnovations including the right to claim such innovations, fileadditional applications, continuations, continuations in part,divisions, and/or the like thereof. As such, it should be understoodthat advantages, embodiments, examples, functional, features, logical,operational, organizational, structural, topological, and/or otheraspects of the disclosure are not to be considered limitations on thedisclosure as defined by the claims or limitations on equivalents to theclaims. It is to be understood that, depending on the particular needsand/or characteristics of a P-STATE individual and/or enterprise user,database configuration and/or relational model, data type, datatransmission and/or network framework, syntax structure, and/or thelike, various embodiments of the P-STATE, may be implemented that enablea great deal of flexibility and customization. For example, aspects ofthe P-STATE may be adapted for system latency reduction. While variousembodiments and discussions of the P-STATE have been directed toprefetching and on-demand fetching user account information, however, itis to be understood that the embodiments described herein may be readilyconfigured and/or customized for a wide variety of other applicationsand/or implementations.

What is claimed is:
 1. A method comprising: receiving a purchase actionat a first client device from a user; creating a cookie associated withthe purchase action; sending the cookie to a cookie database associatedwith a user account at a wallet server, the wallet server separate fromthe client device; sending, from a second user device to the cookiedatabase associated with the user account of the wallet server, arequest for the cookie data related to products viewed by the user inthe previous purchase action on a platform other than the second userdevice; identifying the cookie associated with the request; determininga platform type of the second user device; generating a new cookiecompliant with the platform type of the second user device from theretrieved cookie; sending the generated new cookie to the second userdevice; launching a target for executing the generated new cookie;presenting, using the generated new cookie via a display of the seconduser device kiosk, the product viewed by the user in the previouspurchase action.